home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group00a.txt
/
000100_icon-group-sender _Wed May 17 07:41:46 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2001-01-03
|
3KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) id HAA00700
for icon-group-addresses; Wed, 17 May 2000 07:41:01 -0700 (MST)
Message-Id: <200005171441.HAA00700@baskerville.CS.Arizona.EDU>
From: "Ian Trudel" <ian.trudel@tr.cgocable.ca>
X-Newsgroups: comp.lang.icon
Subject: Re: Is Anyone Working On A Unicode Version Of Icon?
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Date: Wed, 17 May 2000 07:24:25 GMT
X-Complaints-To: abuse@cgocable.ca
X-Trace: carnaval.risq.qc.ca 958548265 24.226.208.172 (Wed, 17 May 2000 03:24:25 EDT)
To: icon-group@optima.CS.Arizona.EDU
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
> I'm some C fellow, but I'm just thinking as an Icon programmer, we should
> get out of any direct contact with C. Hence I'm getting interest in some
> bootstrapping, writting primitives in Icon (which they would be translated
> in C for compilation and linking). If Icon would allow us to write shared
> library, that'd really rocks. We could write some high level primitives
that
> really needs to be written in Icon (only few cases, IMO). Unfortunatly,
> handling shared library is often OS-oriented. Under *NIX, it's pretty
easy,
> but under Windows and OS/2, it requires some special structure. Anyway,
this
> is just a thought!
Oh yeah, I forgot some things. First, Icon generates bytecodes which are
interpreted by the virtual machine. But hey, Java is bytecoded and there is
no executable files? Yeah, right, the virtual machine is copied and the code
is appended or something. That's why a simple "hello world" takes 300k! he
he he. Basically, the problem comes from this issue and the calling
convention. Shared library are modeled from C language and its calling
convention. Icon as no such support! So, adding support for generation of
shared library is like having a special virtual machine that handle calling
convention and "understand" it to run proper procedures. That'd also make
big shared library.. Anyway, if I'd be worrying about something, I would do
for the calling convention thing. ::)
I'm not sure about "how hard" it'd be to do. However, that'd be another cool
thing about Icon. Gee, wouldn't be nice to do plugins for your favorite apps
in Icon?!
see ya,
--
Ian Trudel, aka BackOrder
StarTrip Server Administrator
http://startrip.gene6.com/